Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e008106b7e8cd9fdc2ec797ef95cf9e5d1d0296a9fe6c6f695863374598f2b0

Tx prefix hash: 312ffb13f4ce2b3ca9f95b6ae227dde683c788d05de84988b844a8cfef74e150
Tx public key: 90bbb3ae061fa609aa2993cff8a2b05fcac6bd8afca978fa57e88fcbf8464025
Timestamp: 1624617931 Timestamp [UCT]: 2021-06-25 10:45:31 Age [y:d:h:m:s]: 03:222:09:44:41
Block: 284064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925949 RingCT/type: yes/0
Extra: 0190bbb3ae061fa609aa2993cff8a2b05fcac6bd8afca978fa57e88fcbf846402502110000000b3634f08d000000000000000000

1 output(s) for total of 70.271392719000 dcy

stealth address amount amount idx
00: 44ed78c5f20d2c825deb47c738f630df6f56aa2d3ad91ee3aaae423b17751488 70.271392719000 594801 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": 284074, "vin": [ { "gen": { "height": 284064 } } ], "vout": [ { "amount": 70271392719, "target": { "key": "44ed78c5f20d2c825deb47c738f630df6f56aa2d3ad91ee3aaae423b17751488" } } ], "extra": [ 1, 144, 187, 179, 174, 6, 31, 166, 9, 170, 41, 147, 207, 248, 162, 176, 95, 202, 198, 189, 138, 252, 169, 120, 250, 87, 232, 143, 203, 248, 70, 64, 37, 2, 17, 0, 0, 0, 11, 54, 52, 240, 141, 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