Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bdcbeca9b2aebbfa7e57f6fdcc151c427a26326e84c4362ef5c4817f510be676

Tx prefix hash: fb1b0d4ef778736bfe506ee918804e502b7a913bf4388ac083a949fcb4a360f5
Tx public key: 7c7552a3a87225131c281dd5b61403f7d44adaf8dbc2b634a021bd8b0f4f51a7
Timestamp: 1760408869 Timestamp [UCT]: 2025-10-14 02:27:49 Age [y:d:h:m:s]: 00:025:21:02:18
Block: 1389466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18506 RingCT/type: yes/0
Extra: 017c7552a3a87225131c281dd5b61403f7d44adaf8dbc2b634a021bd8b0f4f51a70211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8b4926c612c848a48b8524640b307b4003ca0e25411f8953901aaa89dbef810 0.600000000000 1877695 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1389476, "vin": [ { "gen": { "height": 1389466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8b4926c612c848a48b8524640b307b4003ca0e25411f8953901aaa89dbef810" } } ], "extra": [ 1, 124, 117, 82, 163, 168, 114, 37, 19, 28, 40, 29, 213, 182, 20, 3, 247, 212, 74, 218, 248, 219, 194, 182, 52, 160, 33, 189, 139, 15, 79, 81, 167, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8