Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ddd8eea2b01dc22988d69bfc32674d4b728a3d7e8eb34557235ffd381c27bb8

Tx prefix hash: 0b51e5ec2e922650e83930c07a4f07f0ebebf1a158e1925c03ebd84da15f6456
Tx public key: 7c8a394c1c5ef6100c52031d6d6bced2100c34b93eb0ad79379a4ccf9d96bf36
Timestamp: 1718974441 Timestamp [UCT]: 2024-06-21 12:54:01 Age [y:d:h:m:s]: 00:292:23:42:37
Block: 1049023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209398 RingCT/type: yes/0
Extra: 017c8a394c1c5ef6100c52031d6d6bced2100c34b93eb0ad79379a4ccf9d96bf3602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59d49a282a13dea55fc95586a283e80e9f6dbbd356fac108ef7580a0e1ae387d 0.600000000000 1519120 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": 1049033, "vin": [ { "gen": { "height": 1049023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59d49a282a13dea55fc95586a283e80e9f6dbbd356fac108ef7580a0e1ae387d" } } ], "extra": [ 1, 124, 138, 57, 76, 28, 94, 246, 16, 12, 82, 3, 29, 109, 107, 206, 210, 16, 12, 52, 185, 62, 176, 173, 121, 55, 154, 76, 207, 157, 150, 191, 54, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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