Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 436d49a3b2afb589d6bd316dc9007036aa27787fd61bce946cc035f3a9e052f6

Tx prefix hash: 7ae6485ad5de3a64ea14adb7befe225dd843244a23cccdbfa7a857c667cdd7fd
Tx public key: 105c8c6700057e1f3021990a8f31799944eaec995d4c96080e783364c49d1dda
Timestamp: 1716515736 Timestamp [UCT]: 2024-05-24 01:55:36 Age [y:d:h:m:s]: 00:305:22:58:13
Block: 1028681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218638 RingCT/type: yes/0
Extra: 01105c8c6700057e1f3021990a8f31799944eaec995d4c96080e783364c49d1dda02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27a0816e2611d7d34c56b8c84d0e3f86a1a0b7efeb26d4b214dbf713601b1064 0.600000000000 1496678 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": 1028691, "vin": [ { "gen": { "height": 1028681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27a0816e2611d7d34c56b8c84d0e3f86a1a0b7efeb26d4b214dbf713601b1064" } } ], "extra": [ 1, 16, 92, 140, 103, 0, 5, 126, 31, 48, 33, 153, 10, 143, 49, 121, 153, 68, 234, 236, 153, 93, 76, 150, 8, 14, 120, 51, 100, 196, 157, 29, 218, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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