Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f48d2901f748d66b832aa2f44683430ec038527754fdb27dd74de2a0287c54e

Tx prefix hash: 287ba9f45efc548de6e84e985dfc20bb0f8c4947e92034a87edb120d4b5e55dc
Tx public key: c43f43da29484f7abcd3f87c1674f90790accb056cf522a8b75ce3a3e517d598
Timestamp: 1729198877 Timestamp [UCT]: 2024-10-17 21:01:17 Age [y:d:h:m:s]: 00:224:18:16:10
Block: 1133822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160462 RingCT/type: yes/0
Extra: 01c43f43da29484f7abcd3f87c1674f90790accb056cf522a8b75ce3a3e517d598021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b153d48c17a5510d1a797e6098075083f36d09c07400eacce53473bfee6b3c0 0.600000000000 1617027 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": 1133832, "vin": [ { "gen": { "height": 1133822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b153d48c17a5510d1a797e6098075083f36d09c07400eacce53473bfee6b3c0" } } ], "extra": [ 1, 196, 63, 67, 218, 41, 72, 79, 122, 188, 211, 248, 124, 22, 116, 249, 7, 144, 172, 203, 5, 108, 245, 34, 168, 183, 92, 227, 163, 229, 23, 213, 152, 2, 17, 0, 0, 0, 3, 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