Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 076ca4a4405b000b0a37f4dccf04bbb5fa00a05a0a87fbdbb4dcb76fad7881cd

Tx prefix hash: ee833a571d16a9b75a3a9a0da6f3c42b7699a054896962af4ca69bdb481feab1
Tx public key: e548ed44b75d946fe4f663026798eb4cf801ca40ff6e773ac45ba6d4bce25f61
Timestamp: 1577610688 Timestamp [UCT]: 2019-12-29 09:11:28 Age [y:d:h:m:s]: 04:156:07:25:23
Block: 34185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1000659 RingCT/type: yes/0
Extra: 01e548ed44b75d946fe4f663026798eb4cf801ca40ff6e773ac45ba6d4bce25f61021100000098ac34bf9e000000000000000000

1 output(s) for total of 472.859109793000 dcy

stealth address amount amount idx
00: 1d93182fbf30ca96f4460d68e924695aee87d37988a8fda90533c67304da8ae2 472.859109793000 57555 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": 34195, "vin": [ { "gen": { "height": 34185 } } ], "vout": [ { "amount": 472859109793, "target": { "key": "1d93182fbf30ca96f4460d68e924695aee87d37988a8fda90533c67304da8ae2" } } ], "extra": [ 1, 229, 72, 237, 68, 183, 93, 148, 111, 228, 246, 99, 2, 103, 152, 235, 76, 248, 1, 202, 64, 255, 110, 119, 58, 196, 91, 166, 212, 188, 226, 95, 97, 2, 17, 0, 0, 0, 152, 172, 52, 191, 158, 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