Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23ebcb5896f92bd624e03fd2a39602f30f6396fc3ca3ceedd09767781398e54

Tx prefix hash: 4513ae0c3c858ece19385efdbdc9c9e62138890649b2cdf6db50bddb013bec24
Tx public key: 1a6119dec4e610e164a95840d63678ce3b47ea24e259a0f80285d0ba4e41bd2b
Timestamp: 1731425934 Timestamp [UCT]: 2024-11-12 15:38:54 Age [y:d:h:m:s]: 00:136:20:52:27
Block: 1152191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97644 RingCT/type: yes/0
Extra: 011a6119dec4e610e164a95840d63678ce3b47ea24e259a0f80285d0ba4e41bd2b021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6a6f94d8731b713aea0be800d7aee2f31ff35361d4582bf9c95dd6b1adc9ad5 0.600000000000 1637782 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": 1152201, "vin": [ { "gen": { "height": 1152191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6a6f94d8731b713aea0be800d7aee2f31ff35361d4582bf9c95dd6b1adc9ad5" } } ], "extra": [ 1, 26, 97, 25, 222, 196, 230, 16, 225, 100, 169, 88, 64, 214, 54, 120, 206, 59, 71, 234, 36, 226, 89, 160, 248, 2, 133, 208, 186, 78, 65, 189, 43, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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