Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be1465d2e3230043eb39035586927db1de188589d62f836a29f3f1f01ab67e2a

Tx prefix hash: a5984d10cb36e24563554dd8901a0b0247373473f52d86f647f0e2d49062e65e
Tx public key: 8f83b85d03259f4023152c4feac73e38ac55e7379dfb7f2e25a7cb955ceb23e7
Timestamp: 1709416554 Timestamp [UCT]: 2024-03-02 21:55:54 Age [y:d:h:m:s]: 01:032:14:30:06
Block: 969821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284301 RingCT/type: yes/0
Extra: 018f83b85d03259f4023152c4feac73e38ac55e7379dfb7f2e25a7cb955ceb23e70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21781f0fccc3b5672c87d2bda1997f3ae630d810127e439a57b91e2bb0169b42 0.600000000000 1429670 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": 969831, "vin": [ { "gen": { "height": 969821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21781f0fccc3b5672c87d2bda1997f3ae630d810127e439a57b91e2bb0169b42" } } ], "extra": [ 1, 143, 131, 184, 93, 3, 37, 159, 64, 35, 21, 44, 79, 234, 199, 62, 56, 172, 85, 231, 55, 157, 251, 127, 46, 37, 167, 203, 149, 92, 235, 35, 231, 2, 17, 0, 0, 0, 1, 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