Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05befc7bf2ac71be4bef1a5f6117916adb23e2842120c007e23bf6378fa8d319

Tx prefix hash: b3f836f6f9f5ceae282c95507dcac6bf2eddf26301f5df4c4ca7a216f18b7b23
Tx public key: bc3df108b64789dc12192fc077187de7b5d2c01b67d75a645e4bacc33b211ad8
Timestamp: 1719551799 Timestamp [UCT]: 2024-06-28 05:16:39 Age [y:d:h:m:s]: 01:137:04:34:57
Block: 1053836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356596 RingCT/type: yes/0
Extra: 01bc3df108b64789dc12192fc077187de7b5d2c01b67d75a645e4bacc33b211ad80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40e2107f50be705dcd16a8cfaec0967be9d7b7e42bbf771d8a4a4444282f22bb 0.600000000000 1524187 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": 1053846, "vin": [ { "gen": { "height": 1053836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40e2107f50be705dcd16a8cfaec0967be9d7b7e42bbf771d8a4a4444282f22bb" } } ], "extra": [ 1, 188, 61, 241, 8, 182, 71, 137, 220, 18, 25, 47, 192, 119, 24, 125, 231, 181, 210, 192, 27, 103, 215, 90, 100, 94, 75, 172, 195, 59, 33, 26, 216, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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