Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb3b84de7446575f0862b62006b634bd6b2ad74242b1cef8a4070f390dfcb24e

Tx prefix hash: 93187ad4ad4c3e67db174b874f79235dd0842c63f0057d77f6c2137aa2591ff4
Tx public key: 94922ae738081a317fe56a0003eac4e0afe857eb876ad94273ab3f50e9065dfe
Timestamp: 1682353310 Timestamp [UCT]: 2023-04-24 16:21:50 Age [y:d:h:m:s]: 02:003:16:21:35
Block: 745695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524768 RingCT/type: yes/0
Extra: 0194922ae738081a317fe56a0003eac4e0afe857eb876ad94273ab3f50e9065dfe021100000003faf35c9c000000000000000000

1 output(s) for total of 2.075884192000 dcy

stealth address amount amount idx
00: 4ee0c486e1c4e6256e767555d52bcd17ef7ebc43e69f5dc304e684a44f4a80c7 2.075884192000 1193168 of 0

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": 745705, "vin": [ { "gen": { "height": 745695 } } ], "vout": [ { "amount": 2075884192, "target": { "key": "4ee0c486e1c4e6256e767555d52bcd17ef7ebc43e69f5dc304e684a44f4a80c7" } } ], "extra": [ 1, 148, 146, 42, 231, 56, 8, 26, 49, 127, 229, 106, 0, 3, 234, 196, 224, 175, 232, 87, 235, 135, 106, 217, 66, 115, 171, 63, 80, 233, 6, 93, 254, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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