Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07ede69538c2b54cbb783d0a8ec07c1111190a6e2c1546163e1bdfca16b9d36

Tx prefix hash: 8e8b2244f044cb762291eaa222004ce1fd8c0e6450b42bb0aff849b6640d219d
Tx public key: a6ce4c03d7a588b5adb8208173ad640101a83754d7c75dea4f3b010bce2122e4
Timestamp: 1762522286 Timestamp [UCT]: 2025-11-07 13:31:26 Age [y:d:h:m:s]: 00:046:04:26:18
Block: 1406959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33068 RingCT/type: yes/0
Extra: 01a6ce4c03d7a588b5adb8208173ad640101a83754d7c75dea4f3b010bce2122e402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45f3baaa2a4a3b8e41fd01f7f79ea61ee357fea29a44ffd3a721d5e765f58be0 0.600000000000 1895348 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": 1406969, "vin": [ { "gen": { "height": 1406959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45f3baaa2a4a3b8e41fd01f7f79ea61ee357fea29a44ffd3a721d5e765f58be0" } } ], "extra": [ 1, 166, 206, 76, 3, 215, 165, 136, 181, 173, 184, 32, 129, 115, 173, 100, 1, 1, 168, 55, 84, 215, 199, 93, 234, 79, 59, 1, 11, 206, 33, 34, 228, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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