Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a95bb048ac5d95a7008cf61f55dcc471b791e4b857a3fb25b0076a1ead8725

Tx prefix hash: 9a99a5d6a81b01501b8297a3cc08dd67703d856e1f9e0bb29236d226ef5aec55
Tx public key: 9f1b96c901e6f818dd19ff0b356a3287dec859acf93e35322c35555b8fab593d
Timestamp: 1724882539 Timestamp [UCT]: 2024-08-28 22:02:19 Age [y:d:h:m:s]: 00:229:17:19:34
Block: 1098030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164044 RingCT/type: yes/0
Extra: 019f1b96c901e6f818dd19ff0b356a3287dec859acf93e35322c35555b8fab593d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5afbf91353a8ca3b64cc3e83c1584fa694201474e1a65d3560055b694959b7e7 0.600000000000 1573605 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": 1098040, "vin": [ { "gen": { "height": 1098030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5afbf91353a8ca3b64cc3e83c1584fa694201474e1a65d3560055b694959b7e7" } } ], "extra": [ 1, 159, 27, 150, 201, 1, 230, 248, 24, 221, 25, 255, 11, 53, 106, 50, 135, 222, 200, 89, 172, 249, 62, 53, 50, 44, 53, 85, 91, 143, 171, 89, 61, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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