Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d7b6753981e0cba53c972ec1705557af55e52b65527bf1d2266b670c274b4cf

Tx prefix hash: 5c7a32ab3e455bb5df7bc02574d7132ce48c371795481d3cf4b59a2582a8f6f8
Tx public key: 370e3a4422a5253b7fdc4fadb248d3dac4c2af3b809f3734230114e013f879e9
Timestamp: 1734613939 Timestamp [UCT]: 2024-12-19 13:12:19 Age [y:d:h:m:s]: 00:112:11:06:00
Block: 1178628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80138 RingCT/type: yes/0
Extra: 01370e3a4422a5253b7fdc4fadb248d3dac4c2af3b809f3734230114e013f879e9021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c188f66d48106e4ea34ad5ac7e06634ca05ecfc3a38013b066fbbc8b9338fd 0.600000000000 1665017 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": 1178638, "vin": [ { "gen": { "height": 1178628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c188f66d48106e4ea34ad5ac7e06634ca05ecfc3a38013b066fbbc8b9338fd" } } ], "extra": [ 1, 55, 14, 58, 68, 34, 165, 37, 59, 127, 220, 79, 173, 178, 72, 211, 218, 196, 194, 175, 59, 128, 159, 55, 52, 35, 1, 20, 224, 19, 248, 121, 233, 2, 17, 0, 0, 0, 6, 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