Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d583806b42eae4af9c7bf2125d5eaa60aa4e8dccbd7325f3d8f5bc55ab464ea

Tx prefix hash: 0ca437df036587f6a0f8579096ca70e7a4690167db9b3f4cc54e8b1f619c07f3
Tx public key: ee2c10ffd0299f2835e0fbc0967ebde0137ca8ecec1521aed81ec954f0f8aba6
Timestamp: 1696083168 Timestamp [UCT]: 2023-09-30 14:12:48 Age [y:d:h:m:s]: 01:237:20:44:40
Block: 859473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431096 RingCT/type: yes/0
Extra: 01ee2c10ffd0299f2835e0fbc0967ebde0137ca8ecec1521aed81ec954f0f8aba6021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.871383254000 dcy

stealth address amount amount idx
00: 95d36d3f9bbc741ddb459d292d3b401d86ab57a043ce05d1298cd1d2a3062712 0.871383254000 1313701 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": 859483, "vin": [ { "gen": { "height": 859473 } } ], "vout": [ { "amount": 871383254, "target": { "key": "95d36d3f9bbc741ddb459d292d3b401d86ab57a043ce05d1298cd1d2a3062712" } } ], "extra": [ 1, 238, 44, 16, 255, 208, 41, 159, 40, 53, 224, 251, 192, 150, 126, 189, 224, 19, 124, 168, 236, 236, 21, 33, 174, 216, 30, 201, 84, 240, 248, 171, 166, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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