Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bcea16731ffa999386fc0a81065e938e58fdd37a8e0aded4dd4b82ab252ab1b

Tx prefix hash: e42a4ec6015cfd83cb145e6bb263e3ece53835c9d70831930128d436e1640424
Tx public key: fca10f4dbe964b32b6be4918c4dd5ece36b6d8aa4767afa1a9c9eecd978402c5
Timestamp: 1702895872 Timestamp [UCT]: 2023-12-18 10:37:52 Age [y:d:h:m:s]: 00:332:16:39:10
Block: 915754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238208 RingCT/type: yes/0
Extra: 01fca10f4dbe964b32b6be4918c4dd5ece36b6d8aa4767afa1a9c9eecd978402c502110000001175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d1cdf1e3306fa9812147cf9b0c4fcf040d00cabec37a72aa16b5cc91e135913 0.600000000000 1373178 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": 915764, "vin": [ { "gen": { "height": 915754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d1cdf1e3306fa9812147cf9b0c4fcf040d00cabec37a72aa16b5cc91e135913" } } ], "extra": [ 1, 252, 161, 15, 77, 190, 150, 75, 50, 182, 190, 73, 24, 196, 221, 94, 206, 54, 182, 216, 170, 71, 103, 175, 161, 169, 201, 238, 205, 151, 132, 2, 197, 2, 17, 0, 0, 0, 17, 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