Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aecc4988c006c2c2f55dc29189f52a678d1735047ee4c239e78d42d98319a1b8

Tx prefix hash: 780d8ff02196a33208478ac7e3e1d5815fd6fdd75b8af2e51bebc25ee30979fb
Tx public key: 3e6821d69d28d48dd83c7c79dc4060d2f8d5857b0918f5d27b15287617542c78
Timestamp: 1737524029 Timestamp [UCT]: 2025-01-22 05:33:49 Age [y:d:h:m:s]: 00:146:10:56:22
Block: 1202641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104423 RingCT/type: yes/0
Extra: 013e6821d69d28d48dd83c7c79dc4060d2f8d5857b0918f5d27b15287617542c78021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad64ed74d6a35ff909b17de0c9e74523b4036fbd47221cef346b1863bce35eb2 0.600000000000 1689306 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": 1202651, "vin": [ { "gen": { "height": 1202641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad64ed74d6a35ff909b17de0c9e74523b4036fbd47221cef346b1863bce35eb2" } } ], "extra": [ 1, 62, 104, 33, 214, 157, 40, 212, 141, 216, 60, 124, 121, 220, 64, 96, 210, 248, 213, 133, 123, 9, 24, 245, 210, 123, 21, 40, 118, 23, 84, 44, 120, 2, 17, 0, 0, 0, 4, 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