Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d079574c0c84d5a8df41ae875799c14a936f0ab152463ab636b0f14231281af1

Tx prefix hash: d44dce5460e9412b96335c6d2574d7569ed74b4cbc9228599cd958e68b773de0
Tx public key: dadd1f925bf725c632aba56e376b1cb2507d3d80fc674d51d5b827556f48ee37
Timestamp: 1582502057 Timestamp [UCT]: 2020-02-23 23:54:17 Age [y:d:h:m:s]: 04:279:02:40:52
Block: 70987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092263 RingCT/type: yes/0
Extra: 01dadd1f925bf725c632aba56e376b1cb2507d3d80fc674d51d5b827556f48ee37021100000003d81c26c0000000000000000000

1 output(s) for total of 357.101276908000 dcy

stealth address amount amount idx
00: bc4dba80f26f4e63c0a866aebd416c2ef078f645035edac6beae44f006daf817 357.101276908000 131234 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": 70997, "vin": [ { "gen": { "height": 70987 } } ], "vout": [ { "amount": 357101276908, "target": { "key": "bc4dba80f26f4e63c0a866aebd416c2ef078f645035edac6beae44f006daf817" } } ], "extra": [ 1, 218, 221, 31, 146, 91, 247, 37, 198, 50, 171, 165, 110, 55, 107, 28, 178, 80, 125, 61, 128, 252, 103, 77, 81, 213, 184, 39, 85, 111, 72, 238, 55, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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