Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2c5e83755fefeed94514743f7b82126857f4d487dd8a65a63670b84813f553a

Tx prefix hash: ab810f97430d51c74421f68bb2db0bb7dc101a5d1f01aa9fb7f8bfb673ea485e
Tx public key: d5784b601a59d374ac30f98c0401b9bf0ea86e6d193f6945c553904c395083a4
Timestamp: 1580976786 Timestamp [UCT]: 2020-02-06 08:13:06 Age [y:d:h:m:s]: 05:034:16:03:49
Block: 59670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176937 RingCT/type: yes/0
Extra: 01d5784b601a59d374ac30f98c0401b9bf0ea86e6d193f6945c553904c395083a4021100000023c71d3ff9000000000000000000

1 output(s) for total of 389.330053652000 dcy

stealth address amount amount idx
00: ed777b239d4674ed3a6a70281581403dcc69235aa20b5567965c115c30cc9771 389.330053652000 110134 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": 59680, "vin": [ { "gen": { "height": 59670 } } ], "vout": [ { "amount": 389330053652, "target": { "key": "ed777b239d4674ed3a6a70281581403dcc69235aa20b5567965c115c30cc9771" } } ], "extra": [ 1, 213, 120, 75, 96, 26, 89, 211, 116, 172, 48, 249, 140, 4, 1, 185, 191, 14, 168, 110, 109, 25, 63, 105, 69, 197, 83, 144, 76, 57, 80, 131, 164, 2, 17, 0, 0, 0, 35, 199, 29, 63, 249, 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