Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa85913a502f185d7b9e8a0d43659523f2efa468513f2de6c07ba675b097b6a

Tx prefix hash: c9fe31dfa9e906f9a72bf0a3a8a07c1f3d0ece646b55e5df557ad3fe8773f285
Tx public key: 435167a7f204c660d71dada37fda66a2d903e63aac0ecced287683effe457e28
Timestamp: 1730012547 Timestamp [UCT]: 2024-10-27 07:02:27 Age [y:d:h:m:s]: 00:157:01:16:02
Block: 1140531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112029 RingCT/type: yes/0
Extra: 01435167a7f204c660d71dada37fda66a2d903e63aac0ecced287683effe457e2802110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74e4b4b451d2a8a7bf43574f2353b6ecefad2edfbed9fc6dca5129e3248e9b89 0.600000000000 1624332 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": 1140541, "vin": [ { "gen": { "height": 1140531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74e4b4b451d2a8a7bf43574f2353b6ecefad2edfbed9fc6dca5129e3248e9b89" } } ], "extra": [ 1, 67, 81, 103, 167, 242, 4, 198, 96, 215, 29, 173, 163, 127, 218, 102, 162, 217, 3, 230, 58, 172, 14, 204, 237, 40, 118, 131, 239, 254, 69, 126, 40, 2, 17, 0, 0, 0, 11, 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