Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af684c8684510291ae8e9fd9da5b3858c9b82a7e8931f3ebe437f8228a9ddb30

Tx prefix hash: 558882a3eaf53cfbdf15bb6bd617eeedb69a35b70daedaff933205909adb2c99
Tx public key: 1c61aa308a58ac68bba92a1b89a44e50aa4122716bb3a017d9843dd23864ac2a
Timestamp: 1731307476 Timestamp [UCT]: 2024-11-11 06:44:36 Age [y:d:h:m:s]: 00:125:03:06:54
Block: 1151214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89261 RingCT/type: yes/0
Extra: 011c61aa308a58ac68bba92a1b89a44e50aa4122716bb3a017d9843dd23864ac2a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 675205a7bff2f09f2c706f4d97be5ad1bb8886488e61794c627094c2d5bcb861 0.600000000000 1636703 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": 1151224, "vin": [ { "gen": { "height": 1151214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "675205a7bff2f09f2c706f4d97be5ad1bb8886488e61794c627094c2d5bcb861" } } ], "extra": [ 1, 28, 97, 170, 48, 138, 88, 172, 104, 187, 169, 42, 27, 137, 164, 78, 80, 170, 65, 34, 113, 107, 179, 160, 23, 217, 132, 61, 210, 56, 100, 172, 42, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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