Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74fff5009ccb03111ef1bc8b0c59260140e8eaac90909ce06bf93739f04ea36a

Tx prefix hash: 2253d1544a2271415db29f390f7995b5ee4dd3b74bd4e68601f3a30457985ddd
Tx public key: 80300cde0d2c38eb38d0cc0b28bd21f70f318a539ef912eea393791bac0b11ea
Timestamp: 1733666987 Timestamp [UCT]: 2024-12-08 14:09:47 Age [y:d:h:m:s]: 00:113:11:17:45
Block: 1170770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80875 RingCT/type: yes/0
Extra: 0180300cde0d2c38eb38d0cc0b28bd21f70f318a539ef912eea393791bac0b11ea0211000000024fc18e5d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8795a8d0f29c3e60ad8d44162a7448fb5b62079cae4410d6e2d1c3c50e3aa1d0 0.600000000000 1656503 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": 1170780, "vin": [ { "gen": { "height": 1170770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8795a8d0f29c3e60ad8d44162a7448fb5b62079cae4410d6e2d1c3c50e3aa1d0" } } ], "extra": [ 1, 128, 48, 12, 222, 13, 44, 56, 235, 56, 208, 204, 11, 40, 189, 33, 247, 15, 49, 138, 83, 158, 249, 18, 238, 163, 147, 121, 27, 172, 11, 17, 234, 2, 17, 0, 0, 0, 2, 79, 193, 142, 93, 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