Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695a5c69ac3421b3ccf53b80120b30823e649b92ddcb8b97021c94faabdf6703

Tx prefix hash: 2ee8807a6fd7b7277b0e116b8539320994ba532b65ade081a706048717af2ea1
Tx public key: 24f9984c0de1fce341ecde419250ea73b7ce86090452c477e5b3e4b25d7c0812
Timestamp: 1702583637 Timestamp [UCT]: 2023-12-14 19:53:57 Age [y:d:h:m:s]: 01:150:11:11:30
Block: 913156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368699 RingCT/type: yes/0
Extra: 0124f9984c0de1fce341ecde419250ea73b7ce86090452c477e5b3e4b25d7c081202110000001175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbbe70df05faf746b7a05d79832717fccfb153acefeacc41c741ae87b3f10c1c 0.600000000000 1370402 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": 913166, "vin": [ { "gen": { "height": 913156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbbe70df05faf746b7a05d79832717fccfb153acefeacc41c741ae87b3f10c1c" } } ], "extra": [ 1, 36, 249, 152, 76, 13, 225, 252, 227, 65, 236, 222, 65, 146, 80, 234, 115, 183, 206, 134, 9, 4, 82, 196, 119, 229, 179, 228, 178, 93, 124, 8, 18, 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