Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15fcf3b7845c8acb23d15955ba9131821d5374d4ca1cd33ae470d20f2c968e28

Tx prefix hash: f85d29ef247f1fce04a91609e4f63aa693fdb1390978d0579c8d794b1b67e4af
Tx public key: 2cb40fdac2679b8bc94fbd71011a4df31e76321623a5979a02c950f29edd09c9
Timestamp: 1749783935 Timestamp [UCT]: 2025-06-13 03:05:35 Age [y:d:h:m:s]: 00:160:04:55:54
Block: 1303876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112230 RingCT/type: yes/0
Extra: 012cb40fdac2679b8bc94fbd71011a4df31e76321623a5979a02c950f29edd09c90211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eb50f282e1ed5b4c6640a191a6e888dcf6ab47d6bc422f981e5385d02aa28db 0.600000000000 1791461 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": 1303886, "vin": [ { "gen": { "height": 1303876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eb50f282e1ed5b4c6640a191a6e888dcf6ab47d6bc422f981e5385d02aa28db" } } ], "extra": [ 1, 44, 180, 15, 218, 194, 103, 155, 139, 201, 79, 189, 113, 1, 26, 77, 243, 30, 118, 50, 22, 35, 165, 151, 154, 2, 201, 80, 242, 158, 221, 9, 201, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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