Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 631d69fec2369d382c0c60c27fe405e51eb9721a15c2e7888b6fccce15f87d9a

Tx prefix hash: bbea35a650adb3e88f7fa0535c8999b85e5bbacde9ab7809c9b4408c76936f68
Tx public key: a358231f243e9c79cf6cce96f100596437bb9a2ca726192a0bdf76303ecf59c4
Timestamp: 1712010253 Timestamp [UCT]: 2024-04-01 22:24:13 Age [y:d:h:m:s]: 01:037:02:09:00
Block: 991283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287514 RingCT/type: yes/0
Extra: 01a358231f243e9c79cf6cce96f100596437bb9a2ca726192a0bdf76303ecf59c40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e6ea4889afb25807d4631002d1abc20e5f2f5e820ac02c677a37ccb41bc8653 0.600000000000 1451617 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": 991293, "vin": [ { "gen": { "height": 991283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e6ea4889afb25807d4631002d1abc20e5f2f5e820ac02c677a37ccb41bc8653" } } ], "extra": [ 1, 163, 88, 35, 31, 36, 62, 156, 121, 207, 108, 206, 150, 241, 0, 89, 100, 55, 187, 154, 44, 167, 38, 25, 42, 11, 223, 118, 48, 62, 207, 89, 196, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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