Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec9c25593f612d8531dd25c60cf2c5724c333e5c2270237ed444aa44c2e7b228

Tx prefix hash: 402578e2ff7d7ab6bf9a88d446b1453e557818f783a2704477d4c915b6af7b8d
Tx public key: 0d5b2fd836ea1c6e157e885615b5a1f91f66d2f807e789e648491038ec3cd0ce
Timestamp: 1764434731 Timestamp [UCT]: 2025-11-29 16:45:31 Age [y:d:h:m:s]: 00:004:10:02:30
Block: 1422813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3159 RingCT/type: yes/0
Extra: 010d5b2fd836ea1c6e157e885615b5a1f91f66d2f807e789e648491038ec3cd0ce021100000002da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27e03797fc8ceab8b3c8baaf969112adf75eb10b682295a582995ea249d3270c 0.600000000000 1911386 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": 1422823, "vin": [ { "gen": { "height": 1422813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27e03797fc8ceab8b3c8baaf969112adf75eb10b682295a582995ea249d3270c" } } ], "extra": [ 1, 13, 91, 47, 216, 54, 234, 28, 110, 21, 126, 136, 86, 21, 181, 161, 249, 31, 102, 210, 248, 7, 231, 137, 230, 72, 73, 16, 56, 236, 60, 208, 206, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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