Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f6da0b6ee33b79865aa3633a9de1ad2225267496b577959a35b2b9ac48e555

Tx prefix hash: b601f7b3cdd4f470e1b3d569adc4931e1fa2e67ca2032ecc7109cb785e184a90
Tx public key: e7f58aec945005e2b7aa17e200f05b7b714e6774bc68817518f894806d067eb4
Timestamp: 1701198195 Timestamp [UCT]: 2023-11-28 19:03:15 Age [y:d:h:m:s]: 01:166:18:12:38
Block: 901679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380360 RingCT/type: yes/0
Extra: 01e7f58aec945005e2b7aa17e200f05b7b714e6774bc68817518f894806d067eb402110000000233af99f4000000000000000000

1 output(s) for total of 0.631485160000 dcy

stealth address amount amount idx
00: 4b2c604895feaf2399c448242c6a48910fd61cf74f5a29ee2aac312c035a0613 0.631485160000 1358262 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": 901689, "vin": [ { "gen": { "height": 901679 } } ], "vout": [ { "amount": 631485160, "target": { "key": "4b2c604895feaf2399c448242c6a48910fd61cf74f5a29ee2aac312c035a0613" } } ], "extra": [ 1, 231, 245, 138, 236, 148, 80, 5, 226, 183, 170, 23, 226, 0, 240, 91, 123, 113, 78, 103, 116, 188, 104, 129, 117, 24, 248, 148, 128, 109, 6, 126, 180, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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