Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 491229ab07d43abc475ab728543b2728e59950235cfe74a8a9f73154c8cf94c4

Tx prefix hash: d41bc800fb5c37d3f2f6a2a1ccf3e292472124e2a981a1882b502d05e11b09c7
Tx public key: 2702dead92355336837c2b4553db152eced8e1b2d511f15d5732eaafd258c95f
Timestamp: 1738234094 Timestamp [UCT]: 2025-01-30 10:48:14 Age [y:d:h:m:s]: 00:137:00:46:05
Block: 1208306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97903 RingCT/type: yes/0
Extra: 012702dead92355336837c2b4553db152eced8e1b2d511f15d5732eaafd258c95f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24cc235b20654b008341e2cac5b6addbe05b667e4b483fb830bbd857f354afca 0.600000000000 1695037 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": 1208316, "vin": [ { "gen": { "height": 1208306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24cc235b20654b008341e2cac5b6addbe05b667e4b483fb830bbd857f354afca" } } ], "extra": [ 1, 39, 2, 222, 173, 146, 53, 83, 54, 131, 124, 43, 69, 83, 219, 21, 46, 206, 216, 225, 178, 213, 17, 241, 93, 87, 50, 234, 175, 210, 88, 201, 95, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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