Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f8a1fc8d04d07eb88900cfa088c03aa2dcc7883cf43243fb796ef44840049bc

Tx prefix hash: 3a8af18c4f1e0906dd1cfd339e22115fa791cfc500a388936412aee754658f72
Tx public key: 80475aead4302b00facf8b7d3a99a0f16090c1885f5dd01b6306fbca089a669c
Timestamp: 1712532553 Timestamp [UCT]: 2024-04-07 23:29:13 Age [y:d:h:m:s]: 01:039:00:43:16
Block: 995610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288903 RingCT/type: yes/0
Extra: 0180475aead4302b00facf8b7d3a99a0f16090c1885f5dd01b6306fbca089a669c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c0253bb0ef94bbc046b17bc4091e2c5e34c5dbb0a83418f1fd5806b5986c71f 0.600000000000 1456022 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": 995620, "vin": [ { "gen": { "height": 995610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c0253bb0ef94bbc046b17bc4091e2c5e34c5dbb0a83418f1fd5806b5986c71f" } } ], "extra": [ 1, 128, 71, 90, 234, 212, 48, 43, 0, 250, 207, 139, 125, 58, 153, 160, 241, 96, 144, 193, 136, 95, 93, 208, 27, 99, 6, 251, 202, 8, 154, 102, 156, 2, 17, 0, 0, 0, 3, 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