Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8945ac23930a274ae48b7b9b98f930a6d8da4d7967c5669f51449c6b8f040635

Tx prefix hash: c526729df9c4ee9efdf8ff92f2e21ceada012919573d40850b74935867a9a4ce
Tx public key: ea4191b1e837afd7696c3397ef6744b6481fd94d42a15c71102fe945c32e9f82
Timestamp: 1707179610 Timestamp [UCT]: 2024-02-06 00:33:30 Age [y:d:h:m:s]: 01:108:03:23:40
Block: 951257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338394 RingCT/type: yes/0
Extra: 01ea4191b1e837afd7696c3397ef6744b6481fd94d42a15c71102fe945c32e9f8202110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a398694256b250a4e87f45961168537a3b748c457f03c6115fdf338eca50612 0.600000000000 1409997 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": 951267, "vin": [ { "gen": { "height": 951257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a398694256b250a4e87f45961168537a3b748c457f03c6115fdf338eca50612" } } ], "extra": [ 1, 234, 65, 145, 177, 232, 55, 175, 215, 105, 108, 51, 151, 239, 103, 68, 182, 72, 31, 217, 77, 66, 161, 92, 113, 16, 47, 233, 69, 195, 46, 159, 130, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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