Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33689cfa404c2d59a23d41d9a4445a110fc025bc7291b50c07c1b943f4cf10a0

Tx prefix hash: 7d9f89d8da7780418f8fbe72d0416b90b87fc0769c0122936f41699bc8f38aaa
Tx public key: 5dea1d9c0a2890c6781041f1224351ae55beb7c18a40a3605fc97e49e443491f
Timestamp: 1714030299 Timestamp [UCT]: 2024-04-25 07:31:39 Age [y:d:h:m:s]: 01:039:03:49:31
Block: 1008057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288966 RingCT/type: yes/0
Extra: 015dea1d9c0a2890c6781041f1224351ae55beb7c18a40a3605fc97e49e443491f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5be89cfba446bb576d9f774f99b87da76ac8591e15a7c6bc2c35df6f17a15d 0.600000000000 1469523 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": 1008067, "vin": [ { "gen": { "height": 1008057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5be89cfba446bb576d9f774f99b87da76ac8591e15a7c6bc2c35df6f17a15d" } } ], "extra": [ 1, 93, 234, 29, 156, 10, 40, 144, 198, 120, 16, 65, 241, 34, 67, 81, 174, 85, 190, 183, 193, 138, 64, 163, 96, 95, 201, 126, 73, 228, 67, 73, 31, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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