Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842339b8c51c2beb7631939a48169fa6d09cc900c5eb5b1bb35ddde7584c891b

Tx prefix hash: 9165c2b68591946799a12de4a0cdefc4f46d0f8243837ff56b5cd15a5104b0e5
Tx public key: b9cbea88b04a901302c1acd87bbf7106274d9a4b3b94a826c5e1f682c831745a
Timestamp: 1577914091 Timestamp [UCT]: 2020-01-01 21:28:11 Age [y:d:h:m:s]: 04:363:09:10:34
Block: 36631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148914 RingCT/type: yes/0
Extra: 01b9cbea88b04a901302c1acd87bbf7106274d9a4b3b94a826c5e1f682c831745a0211000000424943cd9f000000000000000000

1 output(s) for total of 464.116644099000 dcy

stealth address amount amount idx
00: 07c686f7e5e69bae53e76ac843a5d7351401fd6ed228c9feffbe396a25afaa8c 464.116644099000 62095 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": 36641, "vin": [ { "gen": { "height": 36631 } } ], "vout": [ { "amount": 464116644099, "target": { "key": "07c686f7e5e69bae53e76ac843a5d7351401fd6ed228c9feffbe396a25afaa8c" } } ], "extra": [ 1, 185, 203, 234, 136, 176, 74, 144, 19, 2, 193, 172, 216, 123, 191, 113, 6, 39, 77, 154, 75, 59, 148, 168, 38, 197, 225, 246, 130, 200, 49, 116, 90, 2, 17, 0, 0, 0, 66, 73, 67, 205, 159, 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