Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9500b4ce3ea33e2d435935163e15bd210825f9134143c704d0cd998f4c08610

Tx prefix hash: 61ccb3c042191fd6cbf8d2f5a974f039c95a6724921f1ef931687e3660989964
Tx public key: 8c7839df550f26f5269458c5aea8706fe41ed6a249b9b310503d8912847a8a1d
Timestamp: 1723598136 Timestamp [UCT]: 2024-08-14 01:15:36 Age [y:d:h:m:s]: 00:231:01:54:31
Block: 1087384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165016 RingCT/type: yes/0
Extra: 018c7839df550f26f5269458c5aea8706fe41ed6a249b9b310503d8912847a8a1d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47bb94bd7772d55234758c51279986b366dc9c5384e6d120d9ce03d45b4e2f83 0.600000000000 1561993 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": 1087394, "vin": [ { "gen": { "height": 1087384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47bb94bd7772d55234758c51279986b366dc9c5384e6d120d9ce03d45b4e2f83" } } ], "extra": [ 1, 140, 120, 57, 223, 85, 15, 38, 245, 38, 148, 88, 197, 174, 168, 112, 111, 228, 30, 214, 162, 73, 185, 179, 16, 80, 61, 137, 18, 132, 122, 138, 29, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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