Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c276486324d0231c896e8a785a69171df1b52af2976fde9d9f3f92c6ac136c96

Tx prefix hash: b5a310a98910d257f15acd4f95ec5e3fd464a288ef8825f703b03f488e8efeff
Tx public key: e3230cb3dce94da803016adbdbe5eec7298eab69adedbffc9ab89bf512d1ae80
Timestamp: 1702379667 Timestamp [UCT]: 2023-12-12 11:14:27 Age [y:d:h:m:s]: 01:111:20:35:51
Block: 911490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341061 RingCT/type: yes/0
Extra: 01e3230cb3dce94da803016adbdbe5eec7298eab69adedbffc9ab89bf512d1ae8002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 081b6e5a0cce3fef9913d7371b8b569b1d13f194d1d3c4283bc64a1503eedb2a 0.600000000000 1368694 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": 911500, "vin": [ { "gen": { "height": 911490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "081b6e5a0cce3fef9913d7371b8b569b1d13f194d1d3c4283bc64a1503eedb2a" } } ], "extra": [ 1, 227, 35, 12, 179, 220, 233, 77, 168, 3, 1, 106, 219, 219, 229, 238, 199, 41, 142, 171, 105, 173, 237, 191, 252, 154, 184, 155, 245, 18, 209, 174, 128, 2, 17, 0, 0, 0, 4, 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