Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7072c9539bd9a2c9b9073cf5d0e96f15af88aec80607372d102e62f7a9a96e6e

Tx prefix hash: 69c15b00067d5db9bee05fa8375222b3b3d546d20bc770125ec873a659a47dd3
Tx public key: 9c90ba693e110b7e2778eeddc6fbcde21a3ed54431028a60d07997b14a45e873
Timestamp: 1707975607 Timestamp [UCT]: 2024-02-15 05:40:07 Age [y:d:h:m:s]: 01:056:17:06:08
Block: 957859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301585 RingCT/type: yes/0
Extra: 019c90ba693e110b7e2778eeddc6fbcde21a3ed54431028a60d07997b14a45e8730211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02b1d7861f7402afd9ff0f75a64212b5cc506a498e5b17e4f9e1d27648784d7 0.600000000000 1417210 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": 957869, "vin": [ { "gen": { "height": 957859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02b1d7861f7402afd9ff0f75a64212b5cc506a498e5b17e4f9e1d27648784d7" } } ], "extra": [ 1, 156, 144, 186, 105, 62, 17, 11, 126, 39, 120, 238, 221, 198, 251, 205, 226, 26, 62, 213, 68, 49, 2, 138, 96, 208, 121, 151, 177, 74, 69, 232, 115, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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