Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 473ff8791e3d67ef78c37ad1cf5fa39269fee9f95a0bbc01836d9d2c89893ec6

Tx prefix hash: 817ec20ebaade1ff22cdec4c5adef0dffd373ddad52de2b533d495b0e1b2bd48
Tx public key: 27b09d58f7837365a31beca40fd4873a4b2ae52db243971f85df8d04c7a34583
Timestamp: 1714326847 Timestamp [UCT]: 2024-04-28 17:54:07 Age [y:d:h:m:s]: 00:346:11:41:47
Block: 1010509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247703 RingCT/type: yes/0
Extra: 0127b09d58f7837365a31beca40fd4873a4b2ae52db243971f85df8d04c7a3458302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1607b62cb7f7ac4240c3523c5bd9140404978ee4a2dab57d42015ca59fa6a2eb 0.600000000000 1472491 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": 1010519, "vin": [ { "gen": { "height": 1010509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1607b62cb7f7ac4240c3523c5bd9140404978ee4a2dab57d42015ca59fa6a2eb" } } ], "extra": [ 1, 39, 176, 157, 88, 247, 131, 115, 101, 163, 27, 236, 164, 15, 212, 135, 58, 75, 42, 229, 45, 178, 67, 151, 31, 133, 223, 141, 4, 199, 163, 69, 131, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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