Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d935b7b184339d11c05b1104ee6b0511616693532fc333757db63eb0f474449b

Tx prefix hash: b67cc737175309607d683e691d6b4c944d528728c81e64716a25eefef62f32af
Tx public key: 929660f8d6b26ba31e678f7f8e459cedb8a3706cc1d84fc5512d03228df0ae9b
Timestamp: 1695493487 Timestamp [UCT]: 2023-09-23 18:24:47 Age [y:d:h:m:s]: 01:123:16:40:20
Block: 854574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349665 RingCT/type: yes/0
Extra: 01929660f8d6b26ba31e678f7f8e459cedb8a3706cc1d84fc5512d03228df0ae9b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.904568869000 dcy

stealth address amount amount idx
00: b761b74ef0e02adc3431bab6f1600161e57dc8bae65d75b860db4c2754a2ef08 0.904568869000 1308556 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": 854584, "vin": [ { "gen": { "height": 854574 } } ], "vout": [ { "amount": 904568869, "target": { "key": "b761b74ef0e02adc3431bab6f1600161e57dc8bae65d75b860db4c2754a2ef08" } } ], "extra": [ 1, 146, 150, 96, 248, 214, 178, 107, 163, 30, 103, 143, 127, 142, 69, 156, 237, 184, 163, 112, 108, 193, 216, 79, 197, 81, 45, 3, 34, 141, 240, 174, 155, 2, 17, 0, 0, 0, 4, 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