Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7853d26d61775e961befb35083002430f4cfc1fcac6dbfe5be3730593b73c9

Tx prefix hash: 52396f76c6c4b8c929c1bdd4072c4d0534152be40296c017a7dea872d0a968d2
Tx public key: 713201e3f503e58ad9fce22565c80f8455adb497a1fec6b2064af1e417c94aca
Timestamp: 1715844778 Timestamp [UCT]: 2024-05-16 07:32:58 Age [y:d:h:m:s]: 00:284:16:35:19
Block: 1023114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203444 RingCT/type: yes/0
Extra: 01713201e3f503e58ad9fce22565c80f8455adb497a1fec6b2064af1e417c94aca021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435c16809c3b2829c099a6386ee7c97e79fa3d8280f1b99c2b7deb853c352325 0.600000000000 1487909 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": 1023124, "vin": [ { "gen": { "height": 1023114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435c16809c3b2829c099a6386ee7c97e79fa3d8280f1b99c2b7deb853c352325" } } ], "extra": [ 1, 113, 50, 1, 227, 245, 3, 229, 138, 217, 252, 226, 37, 101, 200, 15, 132, 85, 173, 180, 151, 161, 254, 198, 178, 6, 74, 241, 228, 23, 201, 74, 202, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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