Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23423bd392e1fa98fd32ea0b6432edc13e71305a4eeefd4d52cec6c3f1971fa2

Tx prefix hash: 4b541140c93c524045aee38ae2c54af102c2e9d148c42d1ad7113b3b2a237991
Tx public key: 21be5ab2ca615dc30f2f9e531ec14fb6f8c7e2f7bf8eff43d5e000c7e2917d5f
Timestamp: 1648519188 Timestamp [UCT]: 2022-03-29 01:59:48 Age [y:d:h:m:s]: 03:217:07:19:27
Block: 468605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933236 RingCT/type: yes/0
Extra: 0121be5ab2ca615dc30f2f9e531ec14fb6f8c7e2f7bf8eff43d5e000c7e2917d5f02110000001806faf294000000000000000000

1 output(s) for total of 17.191642021000 dcy

stealth address amount amount idx
00: e9068aa187bae49f9181cc6b882668fbbab49cc9d743f632a82dc3a334753a13 17.191642021000 887357 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": 468615, "vin": [ { "gen": { "height": 468605 } } ], "vout": [ { "amount": 17191642021, "target": { "key": "e9068aa187bae49f9181cc6b882668fbbab49cc9d743f632a82dc3a334753a13" } } ], "extra": [ 1, 33, 190, 90, 178, 202, 97, 93, 195, 15, 47, 158, 83, 30, 193, 79, 182, 248, 199, 226, 247, 191, 142, 255, 67, 213, 224, 0, 199, 226, 145, 125, 95, 2, 17, 0, 0, 0, 24, 6, 250, 242, 148, 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