Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b75e03617e5b7d6b2ece78bca4495eedcbe7dbef94b8a182fe7563fc67089ea

Tx prefix hash: 02869ed2f382d2be8e01b13df132f6d33929c543ea0eb44ca7af6eecd6b4f3ed
Tx public key: 4590525bd67b349d8f088b4b887398ae00ac29d5e4c9226f4cd32252d6597046
Timestamp: 1706352844 Timestamp [UCT]: 2024-01-27 10:54:04 Age [y:d:h:m:s]: 01:065:16:09:32
Block: 944391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308005 RingCT/type: yes/0
Extra: 014590525bd67b349d8f088b4b887398ae00ac29d5e4c9226f4cd32252d659704602110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bddb3d8de7bc264d8aa593bd15eab8b53929cfb8fe6d70377d394e1b030cd4bd 0.600000000000 1402627 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": 944401, "vin": [ { "gen": { "height": 944391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bddb3d8de7bc264d8aa593bd15eab8b53929cfb8fe6d70377d394e1b030cd4bd" } } ], "extra": [ 1, 69, 144, 82, 91, 214, 123, 52, 157, 143, 8, 139, 75, 136, 115, 152, 174, 0, 172, 41, 213, 228, 201, 34, 111, 76, 211, 34, 82, 214, 89, 112, 70, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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