Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03042fbdbeb8c2cec16273a48bfd0a8ee7cb86c5d582c7b156712c5653c97d80

Tx prefix hash: 22f927b484c4b147a63bb6a402621fd94f674519561e8bd6356578aceb51a743
Tx public key: 355b3670fd2f6b2707380e4d5194ce6f96d2880f499e2c8466cdddcceec08d32
Timestamp: 1732299630 Timestamp [UCT]: 2024-11-22 18:20:30 Age [y:d:h:m:s]: 00:001:02:57:04
Block: 1159427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 804 RingCT/type: yes/0
Extra: 01355b3670fd2f6b2707380e4d5194ce6f96d2880f499e2c8466cdddcceec08d32021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23988844c2c88e026f5eb20c42247df0de354ed305a8c345da7ea96167a62413 0.600000000000 1645062 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": 1159437, "vin": [ { "gen": { "height": 1159427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23988844c2c88e026f5eb20c42247df0de354ed305a8c345da7ea96167a62413" } } ], "extra": [ 1, 53, 91, 54, 112, 253, 47, 107, 39, 7, 56, 14, 77, 81, 148, 206, 111, 150, 210, 136, 15, 73, 158, 44, 132, 102, 205, 221, 204, 238, 192, 141, 50, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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