Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b969b7c1e07b65359569dc80ae187f87b3620120ce0d495b59f8a909aeca9aa9

Tx prefix hash: 7e2e21642c813fd4a467a73cc5028fd5fd0fa2a089d8110c245a46d0db4d62e5
Tx public key: d5909c7bbfa0f44d9b1397f97df4711bb101b8a7bf96907322e5964173a6c6d1
Timestamp: 1725837117 Timestamp [UCT]: 2024-09-08 23:11:57 Age [y:d:h:m:s]: 00:105:06:18:31
Block: 1105952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75306 RingCT/type: yes/0
Extra: 01d5909c7bbfa0f44d9b1397f97df4711bb101b8a7bf96907322e5964173a6c6d102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4226fd859e2e0a188bdd3e0e7b40e1042f05bb13c4d60c96a671f10f7b573b78 0.600000000000 1583471 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": 1105962, "vin": [ { "gen": { "height": 1105952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4226fd859e2e0a188bdd3e0e7b40e1042f05bb13c4d60c96a671f10f7b573b78" } } ], "extra": [ 1, 213, 144, 156, 123, 191, 160, 244, 77, 155, 19, 151, 249, 125, 244, 113, 27, 177, 1, 184, 167, 191, 150, 144, 115, 34, 229, 150, 65, 115, 166, 198, 209, 2, 17, 0, 0, 0, 1, 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