Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9879bcb592f7b52f4703f07fed9b2b4bc1b51687025d972bc2fa55909df09b2b

Tx prefix hash: e176063ecb30ba486dfabfcac221f195d1becc297edaa7bdf7a57789bced918e
Tx public key: 9e046c4c6eaec6680d21b7bff3b872bbc23730369df87cb6617398803e8de5b1
Timestamp: 1703053918 Timestamp [UCT]: 2023-12-20 06:31:58 Age [y:d:h:m:s]: 01:021:08:23:53
Block: 917061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276605 RingCT/type: yes/0
Extra: 019e046c4c6eaec6680d21b7bff3b872bbc23730369df87cb6617398803e8de5b1021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c927f6ef1af083455dba156c680453a01200797a40e9c4ac77118fd0c2a5bd 0.600000000000 1374625 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": 917071, "vin": [ { "gen": { "height": 917061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c927f6ef1af083455dba156c680453a01200797a40e9c4ac77118fd0c2a5bd" } } ], "extra": [ 1, 158, 4, 108, 76, 110, 174, 198, 104, 13, 33, 183, 191, 243, 184, 114, 187, 194, 55, 48, 54, 157, 248, 124, 182, 97, 115, 152, 128, 62, 141, 229, 177, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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