Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5be943b534c05c3d49f2ffc1780b9f759b5db97cc2fd3b0cd49addba74c4eb47

Tx prefix hash: b25ddbb33c91e35b374a7bc8a2242d5a892a8e7521a11435a49d4e63d42d5338
Tx public key: f646db4a339db0faf23be1761a2c8a90966f771432d9412848ce0e3df2eb3762
Timestamp: 1711072457 Timestamp [UCT]: 2024-03-22 01:54:17 Age [y:d:h:m:s]: 00:276:14:46:59
Block: 983561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198029 RingCT/type: yes/0
Extra: 01f646db4a339db0faf23be1761a2c8a90966f771432d9412848ce0e3df2eb37620211000000020424019c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d4e1a18d9c622030a26e176fad2bf935f5591efbdd0a6949b9497a79fe31e1a 0.600000000000 1443702 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": 983571, "vin": [ { "gen": { "height": 983561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d4e1a18d9c622030a26e176fad2bf935f5591efbdd0a6949b9497a79fe31e1a" } } ], "extra": [ 1, 246, 70, 219, 74, 51, 157, 176, 250, 242, 59, 225, 118, 26, 44, 138, 144, 150, 111, 119, 20, 50, 217, 65, 40, 72, 206, 14, 61, 242, 235, 55, 98, 2, 17, 0, 0, 0, 2, 4, 36, 1, 156, 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