Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 064c45dc5f8cb7b3c583cf59e88451c60dd77a1fc965a120bc57bbfb517b2197

Tx prefix hash: 6f87606aadc9e6b16fc0f1c0bd6e976bef103690cc1ebbc335b2fe44206027b3
Tx public key: 38988925496995415c8d030f44f8df17c0bfca1515c5ce7a16429df3b8d8b515
Timestamp: 1736891617 Timestamp [UCT]: 2025-01-14 21:53:37 Age [y:d:h:m:s]: 00:340:17:30:13
Block: 1197450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241076 RingCT/type: yes/0
Extra: 0138988925496995415c8d030f44f8df17c0bfca1515c5ce7a16429df3b8d8b515021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 082a05bca67b4fdcc5cf02762044a6853fde6d5dfb7059f852107721ace67ee8 0.600000000000 1684057 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": 1197460, "vin": [ { "gen": { "height": 1197450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "082a05bca67b4fdcc5cf02762044a6853fde6d5dfb7059f852107721ace67ee8" } } ], "extra": [ 1, 56, 152, 137, 37, 73, 105, 149, 65, 92, 141, 3, 15, 68, 248, 223, 23, 192, 191, 202, 21, 21, 197, 206, 122, 22, 66, 157, 243, 184, 216, 181, 21, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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