Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d72a3824af559042665851d0cbf864c0ffa0431a47e5df7607672dc95e0add05

Tx prefix hash: 91c1ed1c8254c5df235f4f1f64b1134acd2810b91c52802471740b4030d7e64c
Tx public key: 020255bbbfb80bf92c8bdc0786770fb2a5819ff1bdad910e4459e76eb9cbcd6f
Timestamp: 1670331099 Timestamp [UCT]: 2022-12-06 12:51:39 Age [y:d:h:m:s]: 02:148:21:36:15
Block: 646666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 628145 RingCT/type: yes/0
Extra: 01020255bbbfb80bf92c8bdc0786770fb2a5819ff1bdad910e4459e76eb9cbcd6f02110000000183600029000000000000000000

1 output(s) for total of 4.419031421000 dcy

stealth address amount amount idx
00: 64b1bb5a7f0b8b77061a1c2b8d92a9bad72561d82fe120c68c940b8206d251cb 4.419031421000 1086901 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": 646676, "vin": [ { "gen": { "height": 646666 } } ], "vout": [ { "amount": 4419031421, "target": { "key": "64b1bb5a7f0b8b77061a1c2b8d92a9bad72561d82fe120c68c940b8206d251cb" } } ], "extra": [ 1, 2, 2, 85, 187, 191, 184, 11, 249, 44, 139, 220, 7, 134, 119, 15, 178, 165, 129, 159, 241, 189, 173, 145, 14, 68, 89, 231, 110, 185, 203, 205, 111, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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