Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd613c30ef0ef8d7cacc74fd0006661a9a8c809696ed091f46236f7f4c4a5375

Tx prefix hash: ce0246c3f7cadd857c8fb3ba17d1197133c5208ac04576f03eae45b2969ea7e3
Tx public key: 47c8001cdfd163c89d9bd99b2890749d12f1f5477673a48827c8a1de1fcaaa5c
Timestamp: 1764237554 Timestamp [UCT]: 2025-11-27 09:59:14 Age [y:d:h:m:s]: 00:026:06:23:57
Block: 1421177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18793 RingCT/type: yes/0
Extra: 0147c8001cdfd163c89d9bd99b2890749d12f1f5477673a48827c8a1de1fcaaa5c0211000000034e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7566cb1f91e17212a2b326bbb11e5ca9d4de83dbe34f40f01ce9c8078dee8745 0.600000000000 1909734 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": 1421187, "vin": [ { "gen": { "height": 1421177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7566cb1f91e17212a2b326bbb11e5ca9d4de83dbe34f40f01ce9c8078dee8745" } } ], "extra": [ 1, 71, 200, 0, 28, 223, 209, 99, 200, 157, 155, 217, 155, 40, 144, 116, 157, 18, 241, 245, 71, 118, 115, 164, 136, 39, 200, 161, 222, 31, 202, 170, 92, 2, 17, 0, 0, 0, 3, 78, 123, 252, 9, 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