Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f426b4713f138bb178b0ee0bb804726e42bd958be5506e54a7a7dbfdfb4b77a9

Tx prefix hash: 53110ab97177f06da510b9c0c11c21a47361a88fe3bc20c673569c4a016ad98e
Tx public key: 854d1f4e27ff1893d0f14e6c9b030fe803c6b04a8eebf77b3ea60e9421abb2ff
Timestamp: 1734091470 Timestamp [UCT]: 2024-12-13 12:04:30 Age [y:d:h:m:s]: 00:185:16:22:20
Block: 1174295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132408 RingCT/type: yes/0
Extra: 01854d1f4e27ff1893d0f14e6c9b030fe803c6b04a8eebf77b3ea60e9421abb2ff021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c12316cd8b4847ecb9bd53ebf82739f89b1e498145c76425c9ab937577e3864 0.600000000000 1660430 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": 1174305, "vin": [ { "gen": { "height": 1174295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c12316cd8b4847ecb9bd53ebf82739f89b1e498145c76425c9ab937577e3864" } } ], "extra": [ 1, 133, 77, 31, 78, 39, 255, 24, 147, 208, 241, 78, 108, 155, 3, 15, 232, 3, 198, 176, 74, 142, 235, 247, 123, 62, 166, 14, 148, 33, 171, 178, 255, 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