Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e763d30947de1e928dfdbb5c80118fd1ef4fe19fb81a7a7504cecf9a0cc3739

Tx prefix hash: 0c939d5ac41f6cbd732a926246a3d81cf6974428c6b579fd06f5e38225c4027d
Tx public key: ca5618bbd5eb2ea0b73e2133f291dcdc31dde94227085531d6571ba5149ef656
Timestamp: 1725543066 Timestamp [UCT]: 2024-09-05 13:31:06 Age [y:d:h:m:s]: 00:252:13:54:18
Block: 1103520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180375 RingCT/type: yes/0
Extra: 01ca5618bbd5eb2ea0b73e2133f291dcdc31dde94227085531d6571ba5149ef65602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 164fc6f5ef249e5e3314c6f8377e1f0a0b73e461623923b0adc7fb9f8e744112 0.600000000000 1580379 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": 1103530, "vin": [ { "gen": { "height": 1103520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "164fc6f5ef249e5e3314c6f8377e1f0a0b73e461623923b0adc7fb9f8e744112" } } ], "extra": [ 1, 202, 86, 24, 187, 213, 235, 46, 160, 183, 62, 33, 51, 242, 145, 220, 220, 49, 221, 233, 66, 39, 8, 85, 49, 214, 87, 27, 165, 20, 158, 246, 86, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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