Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3198d3b58117dff95ff04e370fd3db154e64821010e971bb6891ba89e668c48

Tx prefix hash: 948d9dec8a5344eb86e47362341770794a34f47c117ec7bdc775d4563fbc6a45
Tx public key: f5ea4ae94e77adfbe1bfb4f6a987db69c0bf64ee9f4a3405bbc5223968be65f1
Timestamp: 1715340530 Timestamp [UCT]: 2024-05-10 11:28:50 Age [y:d:h:m:s]: 00:133:20:12:02
Block: 1018929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95866 RingCT/type: yes/0
Extra: 01f5ea4ae94e77adfbe1bfb4f6a987db69c0bf64ee9f4a3405bbc5223968be65f10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c790a5e682c6e612e35ec97f6a757db327521e4cb54df0dbe684a6fca7357e6 0.600000000000 1482754 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": 1018939, "vin": [ { "gen": { "height": 1018929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c790a5e682c6e612e35ec97f6a757db327521e4cb54df0dbe684a6fca7357e6" } } ], "extra": [ 1, 245, 234, 74, 233, 78, 119, 173, 251, 225, 191, 180, 246, 169, 135, 219, 105, 192, 191, 100, 238, 159, 74, 52, 5, 187, 197, 34, 57, 104, 190, 101, 241, 2, 17, 0, 0, 0, 3, 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