Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d3b84dfda4c8aa7fc622d02a93521d2a7f13c15c31a72bc290a8dad48954f9

Tx prefix hash: 4f59b0da5c6804683af66bdc85c3b7fa402dab22ef1c3582501c376665045b06
Tx public key: 0b932cf15c522a0566a3df2646dcf1bbe9546a2b4025386919960e1c64af0ad2
Timestamp: 1697394985 Timestamp [UCT]: 2023-10-15 18:36:25 Age [y:d:h:m:s]: 01:186:15:11:58
Block: 870360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394411 RingCT/type: yes/0
Extra: 010b932cf15c522a0566a3df2646dcf1bbe9546a2b4025386919960e1c64af0ad202110000000136a45730000000000000000000

1 output(s) for total of 0.801929229000 dcy

stealth address amount amount idx
00: b21f15304a02b140e3aed483927fa856062be7781cd99555c9bf72190de36dc7 0.801929229000 1325239 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": 870370, "vin": [ { "gen": { "height": 870360 } } ], "vout": [ { "amount": 801929229, "target": { "key": "b21f15304a02b140e3aed483927fa856062be7781cd99555c9bf72190de36dc7" } } ], "extra": [ 1, 11, 147, 44, 241, 92, 82, 42, 5, 102, 163, 223, 38, 70, 220, 241, 187, 233, 84, 106, 43, 64, 37, 56, 105, 25, 150, 14, 28, 100, 175, 10, 210, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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