Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349da426f0a1b0d66a13e22c1a883466a09205b0b62a5ecc6dc586e1248a124c

Tx prefix hash: 380f73eaf1d7e8cb4edb4bf312da85d77530ed052b214f81c409140af0bb59a8
Tx public key: 8c32ec81a4e548f9b87c9f026f0a37b972d447896b4c4c8715e23e9577a10564
Timestamp: 1588516985 Timestamp [UCT]: 2020-05-03 14:43:05 Age [y:d:h:m:s]: 04:237:00:07:48
Block: 98370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084571 RingCT/type: yes/0
Extra: 018c32ec81a4e548f9b87c9f026f0a37b972d447896b4c4c8715e23e9577a105640211000000044ac5aa02000000000000000000

1 output(s) for total of 289.774469193000 dcy

stealth address amount amount idx
00: d9c7d9e338feaa131d5eda73cc68fecf3879e30159ee3b845fbed3d3107f3473 289.774469193000 173801 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": 98380, "vin": [ { "gen": { "height": 98370 } } ], "vout": [ { "amount": 289774469193, "target": { "key": "d9c7d9e338feaa131d5eda73cc68fecf3879e30159ee3b845fbed3d3107f3473" } } ], "extra": [ 1, 140, 50, 236, 129, 164, 229, 72, 249, 184, 124, 159, 2, 111, 10, 55, 185, 114, 212, 71, 137, 107, 76, 76, 135, 21, 226, 62, 149, 119, 161, 5, 100, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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