Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a9631be09a31f5371b93702ad0867a90d8eb7a1bb9ba3ace7ea218bf6df3b94

Tx prefix hash: 4dedb8fccdfb674ee9e8c2b81f8444b67e61051d888cb8947b37318ca5d8e182
Tx public key: 1edf3583d91d590065b9f77c7a9a34a8f32e16e897dd166dbc7cfed9f85f4ae6
Timestamp: 1714548271 Timestamp [UCT]: 2024-05-01 07:24:31 Age [y:d:h:m:s]: 00:254:22:48:41
Block: 1012358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182489 RingCT/type: yes/0
Extra: 011edf3583d91d590065b9f77c7a9a34a8f32e16e897dd166dbc7cfed9f85f4ae602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04c8b5c8ade9e91477bd5a41f35223a381968d9d1bbbfcdbb848c1615b14fd7b 0.600000000000 1474854 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": 1012368, "vin": [ { "gen": { "height": 1012358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04c8b5c8ade9e91477bd5a41f35223a381968d9d1bbbfcdbb848c1615b14fd7b" } } ], "extra": [ 1, 30, 223, 53, 131, 217, 29, 89, 0, 101, 185, 247, 124, 122, 154, 52, 168, 243, 46, 22, 232, 151, 221, 22, 109, 188, 124, 254, 217, 248, 95, 74, 230, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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