Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb8ba38b4f0591eed60cd07f438596147436da9ecb28cfe6ab2d4f4bb6472e45

Tx prefix hash: 45e2104b573d94b4e7a5f90cceed99d407d2498d0891a80e664e18de56605e0f
Tx public key: af51d22d9535f8dc90cd825e7b0b27e3fd38fdb8b1b941a91a5a71d0c98f8589
Timestamp: 1704112419 Timestamp [UCT]: 2024-01-01 12:33:39 Age [y:d:h:m:s]: 01:098:19:51:34
Block: 925830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331749 RingCT/type: yes/0
Extra: 01af51d22d9535f8dc90cd825e7b0b27e3fd38fdb8b1b941a91a5a71d0c98f85890211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb4725d52617c1a6ad9cc9e5c1d759da9b0fe0f491e40c5b9404d62ec298fba7 0.600000000000 1383600 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": 925840, "vin": [ { "gen": { "height": 925830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb4725d52617c1a6ad9cc9e5c1d759da9b0fe0f491e40c5b9404d62ec298fba7" } } ], "extra": [ 1, 175, 81, 210, 45, 149, 53, 248, 220, 144, 205, 130, 94, 123, 11, 39, 227, 253, 56, 253, 184, 177, 185, 65, 169, 26, 90, 113, 208, 201, 143, 133, 137, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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