Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e454d2660ead6b84dcb47d422e93e285f560de9bc44ab65350cd7fdff09762

Tx prefix hash: 620fc936df1ccfdc393c4933c660f0b8a2cf9a90fde2862b8eddb1e37bee2b07
Tx public key: 55c59bf63fe67faa7bfefd15c1582c8d8d28fe8fae8de30fc9f0193b0aea45d4
Timestamp: 1681141423 Timestamp [UCT]: 2023-04-10 15:43:43 Age [y:d:h:m:s]: 01:277:02:58:46
Block: 735639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459567 RingCT/type: yes/0
Extra: 0155c59bf63fe67faa7bfefd15c1582c8d8d28fe8fae8de30fc9f0193b0aea45d4021100000004e6d27f9c000000000000000000

1 output(s) for total of 2.241417916000 dcy

stealth address amount amount idx
00: 4b071cd2ae5d4cab4f6006ae3f9e3c0e9a0838fe56f60ef8302e2f575f13f804 2.241417916000 1181986 of 0

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": 735649, "vin": [ { "gen": { "height": 735639 } } ], "vout": [ { "amount": 2241417916, "target": { "key": "4b071cd2ae5d4cab4f6006ae3f9e3c0e9a0838fe56f60ef8302e2f575f13f804" } } ], "extra": [ 1, 85, 197, 155, 246, 63, 230, 127, 170, 123, 254, 253, 21, 193, 88, 44, 141, 141, 40, 254, 143, 174, 141, 227, 15, 201, 240, 25, 59, 10, 234, 69, 212, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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