Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55e1600ee0346c1cb10cc88aede3933d163b34644fd2415290d4a148dcbe4aa8

Tx prefix hash: 745e61870810b787e4ac26ea61fa7f29813f2acc7a7b42fb7395ec9a06d4ae14
Tx public key: 6b8f86fcebdde2b69d5fff7eaf983bdcbd863406ba66f98c974bfe13b361e662
Timestamp: 1723712074 Timestamp [UCT]: 2024-08-15 08:54:34 Age [y:d:h:m:s]: 00:084:07:44:42
Block: 1088335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60309 RingCT/type: yes/0
Extra: 016b8f86fcebdde2b69d5fff7eaf983bdcbd863406ba66f98c974bfe13b361e662021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61358a3bd7e730d1df7cf088932dfd23d1ea1fb53d104f50b585dc56e6715a5a 0.600000000000 1562950 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": 1088345, "vin": [ { "gen": { "height": 1088335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61358a3bd7e730d1df7cf088932dfd23d1ea1fb53d104f50b585dc56e6715a5a" } } ], "extra": [ 1, 107, 143, 134, 252, 235, 221, 226, 182, 157, 95, 255, 126, 175, 152, 59, 220, 189, 134, 52, 6, 186, 102, 249, 140, 151, 75, 254, 19, 179, 97, 230, 98, 2, 17, 0, 0, 0, 1, 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