Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779adb9517df97e0d4f41cdacc94cff47f5510de5d72afcce527116b6654ff16

Tx prefix hash: b60b11a3d2fa24a148cde887e9042e4173e17999f9dce40d9269ec29204922f0
Tx public key: ca9ffea7e7d282d5e9713a2d1c53f1f71d3e93b40ef980b0793a113cc9d22fda
Timestamp: 1721754628 Timestamp [UCT]: 2024-07-23 17:10:28 Age [y:d:h:m:s]: 00:260:21:54:10
Block: 1072091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186402 RingCT/type: yes/0
Extra: 01ca9ffea7e7d282d5e9713a2d1c53f1f71d3e93b40ef980b0793a113cc9d22fda02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce382e8ceadb65307e8cb23d1bd54b28d5863a15289950fa6e5cf8e452729e09 0.600000000000 1544538 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": 1072101, "vin": [ { "gen": { "height": 1072091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce382e8ceadb65307e8cb23d1bd54b28d5863a15289950fa6e5cf8e452729e09" } } ], "extra": [ 1, 202, 159, 254, 167, 231, 210, 130, 213, 233, 113, 58, 45, 28, 83, 241, 247, 29, 62, 147, 180, 14, 249, 128, 176, 121, 58, 17, 60, 201, 210, 47, 218, 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