Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbbdb345e85e59dfe1947ed3d2a6430df3d432cc0aab1871029c76232ee5abd4

Tx prefix hash: 784dca92267375f3f5532e45ab8d6bd31f2a3297d8dafbcee29e13bd2ed0c20f
Tx public key: 7d4114dccd7af1c7aa0fac8b11886bfdaae680546a4bc4a1e17096eb10ae7003
Timestamp: 1730087956 Timestamp [UCT]: 2024-10-28 03:59:16 Age [y:d:h:m:s]: 00:185:01:26:24
Block: 1141128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132087 RingCT/type: yes/0
Extra: 017d4114dccd7af1c7aa0fac8b11886bfdaae680546a4bc4a1e17096eb10ae700302110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a18a7f806b6270cf37db310b6c7ad07f48b29c061c81a8c36ffa86d8e227eb 0.600000000000 1624935 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": 1141138, "vin": [ { "gen": { "height": 1141128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a18a7f806b6270cf37db310b6c7ad07f48b29c061c81a8c36ffa86d8e227eb" } } ], "extra": [ 1, 125, 65, 20, 220, 205, 122, 241, 199, 170, 15, 172, 139, 17, 136, 107, 253, 170, 230, 128, 84, 106, 75, 196, 161, 225, 112, 150, 235, 16, 174, 112, 3, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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