Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a442feff4ca185e9adbd3ddedaa723e433420a75c3434eb6230814cc6690eeb8

Tx prefix hash: 70234572f9fed8f94c6ce5230ab174c6a42d0a736215c3195e651018e80112d8
Tx public key: 52a6ea3ed265e62ddb0e3df5fe8da6974e3b289ad821e76ea29ed5bd2d81d0bb
Timestamp: 1705790234 Timestamp [UCT]: 2024-01-20 22:37:14 Age [y:d:h:m:s]: 01:146:12:37:32
Block: 939720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365775 RingCT/type: yes/0
Extra: 0152a6ea3ed265e62ddb0e3df5fe8da6974e3b289ad821e76ea29ed5bd2d81d0bb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769f2067c6ff28e1f2f3564fd69a8071abf458a315882e9c69f1076a24a71c95 0.600000000000 1397832 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": 939730, "vin": [ { "gen": { "height": 939720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769f2067c6ff28e1f2f3564fd69a8071abf458a315882e9c69f1076a24a71c95" } } ], "extra": [ 1, 82, 166, 234, 62, 210, 101, 230, 45, 219, 14, 61, 245, 254, 141, 166, 151, 78, 59, 40, 154, 216, 33, 231, 110, 162, 158, 213, 189, 45, 129, 208, 187, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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