Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc32d3f71da0d243ee40e92655029e0c336483dc9d8a8158a8a62bee0882fff

Tx prefix hash: 0a8c836115e25cc5896c58be68f359bbf9cf0b5145738a4f847f2dacbea6cbb4
Tx public key: 402e1fb4a119839dbdddaa7ce3b5f10be4eb9a1a4ca735b2580edd37597307db
Timestamp: 1735585402 Timestamp [UCT]: 2024-12-30 19:03:22 Age [y:d:h:m:s]: 00:166:11:53:14
Block: 1186635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118731 RingCT/type: yes/0
Extra: 01402e1fb4a119839dbdddaa7ce3b5f10be4eb9a1a4ca735b2580edd37597307db021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f13306cdbff989d8eab2787bc0849ae50a2cdf3b926351cd7e521e1d368475ef 0.600000000000 1673118 of 15

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": 1186645, "vin": [ { "gen": { "height": 1186635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f13306cdbff989d8eab2787bc0849ae50a2cdf3b926351cd7e521e1d368475ef" } } ], "extra": [ 1, 64, 46, 31, 180, 161, 25, 131, 157, 189, 221, 170, 124, 227, 181, 241, 11, 228, 235, 154, 26, 76, 167, 53, 178, 88, 14, 221, 55, 89, 115, 7, 219, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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