Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3ac1e8c7ed983191b6a41007ceb5d676a275910f6ada325a525657d718630d9

Tx prefix hash: 235e32e097efc5976911fb9bbb7dc3d8f801aa3f52b50cfe17ae750527b6c13e
Tx public key: 3190ca84761d37cc2d03a7fc2490e85ac2ceb04225fa62f5725a7563d659d4ab
Timestamp: 1737243000 Timestamp [UCT]: 2025-01-18 23:30:00 Age [y:d:h:m:s]: 00:057:01:08:54
Block: 1200321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40593 RingCT/type: yes/0
Extra: 013190ca84761d37cc2d03a7fc2490e85ac2ceb04225fa62f5725a7563d659d4ab0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de19fc61a0f6a8dc24db77fbfbee1424d61c806011dfe9e5e76405df1c60bece 0.600000000000 1686964 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": 1200331, "vin": [ { "gen": { "height": 1200321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de19fc61a0f6a8dc24db77fbfbee1424d61c806011dfe9e5e76405df1c60bece" } } ], "extra": [ 1, 49, 144, 202, 132, 118, 29, 55, 204, 45, 3, 167, 252, 36, 144, 232, 90, 194, 206, 176, 66, 37, 250, 98, 245, 114, 90, 117, 99, 214, 89, 212, 171, 2, 17, 0, 0, 0, 2, 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