Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22527b08fafb3707b3aaaedd9eb6f36833faf00dba1d5078f95db42c8eb36cba

Tx prefix hash: eae35430285af788400e88385aea845676f8662b32d763f54abd2d0526936b16
Tx public key: b9f0ae869e3cca21562ead3c5979a8a12bfd89217f0b8d290738080706f40186
Timestamp: 1718034600 Timestamp [UCT]: 2024-06-10 15:50:00 Age [y:d:h:m:s]: 00:201:14:30:36
Block: 1041267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144271 RingCT/type: yes/0
Extra: 01b9f0ae869e3cca21562ead3c5979a8a12bfd89217f0b8d290738080706f401860211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a7542bcb90527672c99c5d23a1e41c3c58d8f6eef8b2ffb8a30462550e27ea 0.600000000000 1509932 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": 1041277, "vin": [ { "gen": { "height": 1041267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a7542bcb90527672c99c5d23a1e41c3c58d8f6eef8b2ffb8a30462550e27ea" } } ], "extra": [ 1, 185, 240, 174, 134, 158, 60, 202, 33, 86, 46, 173, 60, 89, 121, 168, 161, 43, 253, 137, 33, 127, 11, 141, 41, 7, 56, 8, 7, 6, 244, 1, 134, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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