Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f19aaee3614a12d0b85c0fd21dec5dd43fcc238903e3e5197ea72c0020021ae

Tx prefix hash: 3c470dbf6323f86c0bc33d85dd78f9725f85d4fb64f6efce9001d665aa512ca4
Tx public key: 02d19666a9b5d69884e4ca8e40f8b8224b4db2d9c2c1ed835e55d16be35272bd
Timestamp: 1577156691 Timestamp [UCT]: 2019-12-24 03:04:51 Age [y:d:h:m:s]: 05:110:14:19:10
Block: 30298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228974 RingCT/type: yes/0
Extra: 0102d19666a9b5d69884e4ca8e40f8b8224b4db2d9c2c1ed835e55d16be35272bd0211000000038a2ee0d9000000000000000000

1 output(s) for total of 487.092015448000 dcy

stealth address amount amount idx
00: 337b940e4b3be2e9a21263c73f74dff000bac0f2740e945072ec7d721a58eec1 487.092015448000 50026 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": 30308, "vin": [ { "gen": { "height": 30298 } } ], "vout": [ { "amount": 487092015448, "target": { "key": "337b940e4b3be2e9a21263c73f74dff000bac0f2740e945072ec7d721a58eec1" } } ], "extra": [ 1, 2, 209, 150, 102, 169, 181, 214, 152, 132, 228, 202, 142, 64, 248, 184, 34, 75, 77, 178, 217, 194, 193, 237, 131, 94, 85, 209, 107, 227, 82, 114, 189, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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