Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ad4dbbe2890b1f7c8820588c98dc4a349929e125ab9136bcdc56a46c1582a1

Tx prefix hash: 41f8fa329bb8d01d02350a3e02fb715c2e4fa0719dac8a2b71b561dd7a9d9df8
Tx public key: 9aef751f47dc01b86036150a99b963dfb2b9e46e33062432a0f9768da72da03c
Timestamp: 1631715638 Timestamp [UCT]: 2021-09-15 14:20:38 Age [y:d:h:m:s]: 03:262:00:22:47
Block: 334349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 962780 RingCT/type: yes/0
Extra: 019aef751f47dc01b86036150a99b963dfb2b9e46e33062432a0f9768da72da03c021100000001f606afba000000000000000000

1 output(s) for total of 47.881021629000 dcy

stealth address amount amount idx
00: 8bb5d327ad1e179d4a8e69dab69ca9294fe464f76edd2c17b02de93ffb635d36 47.881021629000 689672 of 0

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": 334359, "vin": [ { "gen": { "height": 334349 } } ], "vout": [ { "amount": 47881021629, "target": { "key": "8bb5d327ad1e179d4a8e69dab69ca9294fe464f76edd2c17b02de93ffb635d36" } } ], "extra": [ 1, 154, 239, 117, 31, 71, 220, 1, 184, 96, 54, 21, 10, 153, 185, 99, 223, 178, 185, 228, 110, 51, 6, 36, 50, 160, 249, 118, 141, 167, 45, 160, 60, 2, 17, 0, 0, 0, 1, 246, 6, 175, 186, 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