Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070e3649bc5bd45adcbbc896b514c74438f746202f9caef92d6353f8443aef4a

Tx prefix hash: 27c4905cf1f96ed0e2d733d0524fa46e96cfac49deaae66a390fcf45c183ad97
Tx public key: abc0f05576ebdc93f961d39040db5cb90bbeebafe2910bf4ad023be81ea0b4ca
Timestamp: 1684119980 Timestamp [UCT]: 2023-05-15 03:06:20 Age [y:d:h:m:s]: 01:202:00:25:59
Block: 760348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405800 RingCT/type: yes/0
Extra: 01abc0f05576ebdc93f961d39040db5cb90bbeebafe2910bf4ad023be81ea0b4ca021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.856314806000 dcy

stealth address amount amount idx
00: dab0c70dc9c69861a2be34bb0280fa3db495095d4503a52f680c873e9f72c4fd 1.856314806000 1208951 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": 760358, "vin": [ { "gen": { "height": 760348 } } ], "vout": [ { "amount": 1856314806, "target": { "key": "dab0c70dc9c69861a2be34bb0280fa3db495095d4503a52f680c873e9f72c4fd" } } ], "extra": [ 1, 171, 192, 240, 85, 118, 235, 220, 147, 249, 97, 211, 144, 64, 219, 92, 185, 11, 190, 235, 175, 226, 145, 11, 244, 173, 2, 59, 232, 30, 160, 180, 202, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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