Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ca8893e5c9e9415f9787989801047f845e12fae2f1f3331339daaa480aa642

Tx prefix hash: 96e152a1d2ae40d97c17a08b8b4fb8718ca514a989ec600b62a055d752e2ace9
Tx public key: 161dafe49fd650a0e5fc3170d13ff834b21066adbc5b94744d1fd759fda57c22
Timestamp: 1636602775 Timestamp [UCT]: 2021-11-11 03:52:55 Age [y:d:h:m:s]: 03:167:12:40:37
Block: 371834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898156 RingCT/type: yes/0
Extra: 01161dafe49fd650a0e5fc3170d13ff834b21066adbc5b94744d1fd759fda57c2202110000001042b3953e000000000000000000

1 output(s) for total of 35.971619755000 dcy

stealth address amount amount idx
00: 697e73ee53c56304b87b0158d4dc4aa0b877968aa7a8220d34cb87e390b2eef2 35.971619755000 753386 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": 371844, "vin": [ { "gen": { "height": 371834 } } ], "vout": [ { "amount": 35971619755, "target": { "key": "697e73ee53c56304b87b0158d4dc4aa0b877968aa7a8220d34cb87e390b2eef2" } } ], "extra": [ 1, 22, 29, 175, 228, 159, 214, 80, 160, 229, 252, 49, 112, 209, 63, 248, 52, 178, 16, 102, 173, 188, 91, 148, 116, 77, 31, 215, 89, 253, 165, 124, 34, 2, 17, 0, 0, 0, 16, 66, 179, 149, 62, 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