Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8994a8fe0273230c01fe73ae6819a8561c434331680b9051b3fcbb6a09fa479

Tx prefix hash: aa11d871ce44c7b89071c1888b7d4f6a79767c04b40f01e760e7e95cb2387152
Tx public key: f0ec8fe586af78764a7bd38ba87b8043a1ed86e761d98a28c52ac5131f5d7984
Timestamp: 1740965691 Timestamp [UCT]: 2025-03-03 01:34:51 Age [y:d:h:m:s]: 00:256:22:58:00
Block: 1230902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181404 RingCT/type: yes/0
Extra: 01f0ec8fe586af78764a7bd38ba87b8043a1ed86e761d98a28c52ac5131f5d79840211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd6c2c0571f4684f2cfb4a418d2725ee9a9cd0e93c0f55d321d25460cbbcb93b 0.600000000000 1717805 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": 1230912, "vin": [ { "gen": { "height": 1230902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd6c2c0571f4684f2cfb4a418d2725ee9a9cd0e93c0f55d321d25460cbbcb93b" } } ], "extra": [ 1, 240, 236, 143, 229, 134, 175, 120, 118, 74, 123, 211, 139, 168, 123, 128, 67, 161, 237, 134, 231, 97, 217, 138, 40, 197, 42, 197, 19, 31, 93, 121, 132, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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