Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4116d2f2a0b5b05c1a2b1eac8d9b6752101e014d038eeb4837825c103196545

Tx prefix hash: fa31a6b96b9fa4693565e64b2b4e861523846395c0464ac24ed2016e837cdc51
Tx public key: 1148b51c5651eac0e8e0e562452d8f800ac89113a836db0f9f2d7ebfbfceedee
Timestamp: 1750069821 Timestamp [UCT]: 2025-06-16 10:30:21 Age [y:d:h:m:s]: 00:205:01:42:37
Block: 1306169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144438 RingCT/type: yes/0
Extra: 011148b51c5651eac0e8e0e562452d8f800ac89113a836db0f9f2d7ebfbfceedee02110000001043846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f495e9b7357e2e36e7409ed51b9a95d61e4645bf61f9a940a53dacd31b2e1f 0.600000000000 1793772 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": 1306179, "vin": [ { "gen": { "height": 1306169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f495e9b7357e2e36e7409ed51b9a95d61e4645bf61f9a940a53dacd31b2e1f" } } ], "extra": [ 1, 17, 72, 181, 28, 86, 81, 234, 192, 232, 224, 229, 98, 69, 45, 143, 128, 10, 200, 145, 19, 168, 54, 219, 15, 159, 45, 126, 191, 191, 206, 237, 238, 2, 17, 0, 0, 0, 16, 67, 132, 109, 102, 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