Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 715e30d0a03da8c2ba4bb05a1cc5927da5e3116028e634c9f3739aa721d95a8b

Tx prefix hash: 135f5ae3eeeadaca367632d7fb9d986a3b50ecaad30f3398e8012c7322d723e3
Tx public key: 7894b060a1d924cb2775b306d23b9dc505b08540f22419340545d64d2939e189
Timestamp: 1751275263 Timestamp [UCT]: 2025-06-30 09:21:03 Age [y:d:h:m:s]: 00:140:15:56:52
Block: 1315749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98723 RingCT/type: yes/0
Extra: 017894b060a1d924cb2775b306d23b9dc505b08540f22419340545d64d2939e1890211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f24e12cfadbb0e73458b304be668341bf03b85b773945a914a366fe4ac674bf4 0.600000000000 1803404 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": 1315759, "vin": [ { "gen": { "height": 1315749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f24e12cfadbb0e73458b304be668341bf03b85b773945a914a366fe4ac674bf4" } } ], "extra": [ 1, 120, 148, 176, 96, 161, 217, 36, 203, 39, 117, 179, 6, 210, 59, 157, 197, 5, 176, 133, 64, 242, 36, 25, 52, 5, 69, 214, 77, 41, 57, 225, 137, 2, 17, 0, 0, 0, 3, 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