Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28579925c8218a597c4fcd69c0dd2d6f5e7b5dfce0a1108be76ddfb677fec6ef

Tx prefix hash: eb1c5ba6f5c5f8ff91a3828a18ff3b3987b3a566859db81653ec989617cd1271
Tx public key: 95c62c543748f9c4fbe5ada92c5eb8084977b5a88aef8064b091103eedf7d4ae
Timestamp: 1726809085 Timestamp [UCT]: 2024-09-20 05:11:25 Age [y:d:h:m:s]: 00:065:02:30:38
Block: 1114007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46539 RingCT/type: yes/0
Extra: 0195c62c543748f9c4fbe5ada92c5eb8084977b5a88aef8064b091103eedf7d4ae02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edcc125c813f054a4039017b9bac3042aa569ee74d4f0fd7df26b8da779ab994 0.600000000000 1593804 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": 1114017, "vin": [ { "gen": { "height": 1114007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edcc125c813f054a4039017b9bac3042aa569ee74d4f0fd7df26b8da779ab994" } } ], "extra": [ 1, 149, 198, 44, 84, 55, 72, 249, 196, 251, 229, 173, 169, 44, 94, 184, 8, 73, 119, 181, 168, 138, 239, 128, 100, 176, 145, 16, 62, 237, 247, 212, 174, 2, 17, 0, 0, 0, 10, 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