Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381ff6d90deb45ad4bc3864c5afa007b1f39ab98a3b97bea9675122cca5121be

Tx prefix hash: 6584fb40ac738ac8e9b7320660299b791fcdc3e8740d4454d3589d7089d2dd43
Tx public key: 1ae9e1e04bef72f79e8e0b988c5f4e4896e008c62cf9b0484a0f89b7e38b0d8a
Timestamp: 1730521451 Timestamp [UCT]: 2024-11-02 04:24:11 Age [y:d:h:m:s]: 00:225:01:20:58
Block: 1144692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160641 RingCT/type: yes/0
Extra: 011ae9e1e04bef72f79e8e0b988c5f4e4896e008c62cf9b0484a0f89b7e38b0d8a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ebc60b51e3d36264dc5f3171ef6ca4b53193aadd0646be5f7fdd5b62ef97def 0.600000000000 1628975 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": 1144702, "vin": [ { "gen": { "height": 1144692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ebc60b51e3d36264dc5f3171ef6ca4b53193aadd0646be5f7fdd5b62ef97def" } } ], "extra": [ 1, 26, 233, 225, 224, 75, 239, 114, 247, 158, 142, 11, 152, 140, 95, 78, 72, 150, 224, 8, 198, 44, 249, 176, 72, 74, 15, 137, 183, 227, 139, 13, 138, 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