Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a20ecaa828475525c49f87dc2fa12ec7c5529f4ffb55018075609f248ec9aa9d

Tx prefix hash: 3d6717f03f095e70b436ef5b5e5fac4e1a7e793ce58e35d342ee082b293ed90c
Tx public key: 1111404a40bf1df1c25f1e734df9082ad892e149deaf5dd6c899967e743069ca
Timestamp: 1694240364 Timestamp [UCT]: 2023-09-09 06:19:24 Age [y:d:h:m:s]: 02:059:20:51:19
Block: 844177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562470 RingCT/type: yes/0
Extra: 011111404a40bf1df1c25f1e734df9082ad892e149deaf5dd6c899967e743069ca02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.979244700000 dcy

stealth address amount amount idx
00: 0b13c26d4a9f213bcda973a756b47fa2e831d4ecb334daab3fcb86fe2a2a1976 0.979244700000 1297471 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": 844187, "vin": [ { "gen": { "height": 844177 } } ], "vout": [ { "amount": 979244700, "target": { "key": "0b13c26d4a9f213bcda973a756b47fa2e831d4ecb334daab3fcb86fe2a2a1976" } } ], "extra": [ 1, 17, 17, 64, 74, 64, 191, 29, 241, 194, 95, 30, 115, 77, 249, 8, 42, 216, 146, 225, 73, 222, 175, 93, 214, 200, 153, 150, 126, 116, 48, 105, 202, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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