Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f80fb38e44678783a8381c5240a8758c05a700dde115572c035d619b8cd0f9

Tx prefix hash: 48aa0a55818c1b84de4b7ee55c40442c998f7dde7c364bed5cae48d7cfa3178f
Tx public key: 982f44eb8c1973b2a3305ca06f3cc4aa009aec8e8b8026b0adf0a4c87a393cf6
Timestamp: 1713603244 Timestamp [UCT]: 2024-04-20 08:54:04 Age [y:d:h:m:s]: 00:351:07:08:50
Block: 1004504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251149 RingCT/type: yes/0
Extra: 01982f44eb8c1973b2a3305ca06f3cc4aa009aec8e8b8026b0adf0a4c87a393cf60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68728bcc96fc3230fb4ce51e45520d23fa1068bee8f3db181b4e3b0c44340913 0.600000000000 1465072 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": 1004514, "vin": [ { "gen": { "height": 1004504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68728bcc96fc3230fb4ce51e45520d23fa1068bee8f3db181b4e3b0c44340913" } } ], "extra": [ 1, 152, 47, 68, 235, 140, 25, 115, 178, 163, 48, 92, 160, 111, 60, 196, 170, 0, 154, 236, 142, 139, 128, 38, 176, 173, 240, 164, 200, 122, 57, 60, 246, 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