Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1510b160c412d7531dd1384efb732622a207fad69c8747ffd56f8bbb939ccb56

Tx prefix hash: 41fda421cc7d3b515f574e4c4c02c92243c8d6962191b1132b3883a97334cb68
Tx public key: 3c31f7fed529b9a5f8f201dcfd1e1fd24382465cfecbef0260828785f79d79b7
Timestamp: 1705335142 Timestamp [UCT]: 2024-01-15 16:12:22 Age [y:d:h:m:s]: 01:136:16:32:55
Block: 935963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358831 RingCT/type: yes/0
Extra: 013c31f7fed529b9a5f8f201dcfd1e1fd24382465cfecbef0260828785f79d79b70211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4231e56b1c4e101cf6f4c64cc33bad2cc93c5a386affdfad421c046cf5a6527c 0.600000000000 1393985 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": 935973, "vin": [ { "gen": { "height": 935963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4231e56b1c4e101cf6f4c64cc33bad2cc93c5a386affdfad421c046cf5a6527c" } } ], "extra": [ 1, 60, 49, 247, 254, 213, 41, 185, 165, 248, 242, 1, 220, 253, 30, 31, 210, 67, 130, 70, 92, 254, 203, 239, 2, 96, 130, 135, 133, 247, 157, 121, 183, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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