Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c12c5491a909cc211c5fbd7eaf63a78afa1968d480cb61795a291221dc7a3ef9

Tx prefix hash: fcb4fcbfeca8eb545402d4bd79c71fec5616b49f190ceaf7ee499fb3be748d18
Tx public key: 6c9348098033eae6862a8c6164186ca72981db262fa526abd5c2b5f227fb4d97
Timestamp: 1702648504 Timestamp [UCT]: 2023-12-15 13:55:04 Age [y:d:h:m:s]: 01:036:09:29:07
Block: 913697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287328 RingCT/type: yes/0
Extra: 016c9348098033eae6862a8c6164186ca72981db262fa526abd5c2b5f227fb4d9702110000000b33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1520ad71ea69990ed4bd1b1b603e78bb5ac47f01d570bb8ef5d4a418d970c99b 0.600000000000 1370973 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": 913707, "vin": [ { "gen": { "height": 913697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1520ad71ea69990ed4bd1b1b603e78bb5ac47f01d570bb8ef5d4a418d970c99b" } } ], "extra": [ 1, 108, 147, 72, 9, 128, 51, 234, 230, 134, 42, 140, 97, 100, 24, 108, 167, 41, 129, 219, 38, 47, 165, 38, 171, 213, 194, 181, 242, 39, 251, 77, 151, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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