Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50cc6c65a86e93dab80e25a7c382b50cbf63730b1bbd713e49b0542eb8efe562

Tx prefix hash: 3baacfd1f6663035c1c32cb90ec1b531c906658a393fdd528bbb2a48e0a436ef
Tx public key: d60596dc6b95ef68b9353934a51a5b9685a7ddfd6d199a13697bb078f876072c
Timestamp: 1746441853 Timestamp [UCT]: 2025-05-05 10:44:13 Age [y:d:h:m:s]: 00:198:05:30:11
Block: 1276238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139394 RingCT/type: yes/0
Extra: 01d60596dc6b95ef68b9353934a51a5b9685a7ddfd6d199a13697bb078f876072c021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c6b97d7f08d8f7d8752da5deb2916a3a39dd4bc24cfa947b9ec0b2166a9fc25 0.600000000000 1763563 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": 1276248, "vin": [ { "gen": { "height": 1276238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c6b97d7f08d8f7d8752da5deb2916a3a39dd4bc24cfa947b9ec0b2166a9fc25" } } ], "extra": [ 1, 214, 5, 150, 220, 107, 149, 239, 104, 185, 53, 57, 52, 165, 26, 91, 150, 133, 167, 221, 253, 109, 25, 154, 19, 105, 123, 176, 120, 248, 118, 7, 44, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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