Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 489f3c7c394b6c93c5bb8800b6fc972475f5ac91b6f27eb9357fc2bd8c2810e6

Tx prefix hash: 6ac0e55fd34d79fe6b69193581e481f313119d2d4f8f7fc3567b678ea89369f8
Tx public key: f47bc83eaf607215345dd0f3131bc469070b993fafb5a376f3559478e2961768
Timestamp: 1730024294 Timestamp [UCT]: 2024-10-27 10:18:14 Age [y:d:h:m:s]: 00:027:18:24:17
Block: 1140626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19827 RingCT/type: yes/0
Extra: 01f47bc83eaf607215345dd0f3131bc469070b993fafb5a376f3559478e2961768021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9e3e9b7bb4daa3f3ee35a602c54029dbc6c8c0a277b3f81afc1065b16630d7 0.600000000000 1624427 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": 1140636, "vin": [ { "gen": { "height": 1140626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9e3e9b7bb4daa3f3ee35a602c54029dbc6c8c0a277b3f81afc1065b16630d7" } } ], "extra": [ 1, 244, 123, 200, 62, 175, 96, 114, 21, 52, 93, 208, 243, 19, 27, 196, 105, 7, 11, 153, 63, 175, 181, 163, 118, 243, 85, 148, 120, 226, 150, 23, 104, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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