Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669800bf534357f95043481de42aaa5b48b9e3c1ae3537f2e9a4548c1ec45611

Tx prefix hash: e26d563ec4065bff8f6d546c701abfe91c6a5ff89b2220882484bda2456ae489
Tx public key: f72d828759e81d94a88adef25b37ad4982d4d6382b6e24ed6a81ca652f435a8a
Timestamp: 1700785801 Timestamp [UCT]: 2023-11-24 00:30:01 Age [y:d:h:m:s]: 01:173:19:19:18
Block: 898250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385422 RingCT/type: yes/0
Extra: 01f72d828759e81d94a88adef25b37ad4982d4d6382b6e24ed6a81ca652f435a8a021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.648223624000 dcy

stealth address amount amount idx
00: a918a4a0a9882047261ff3aba6fa704d10590238685064c95888f0c1e4e03aeb 0.648223624000 1354661 of 0

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": 898260, "vin": [ { "gen": { "height": 898250 } } ], "vout": [ { "amount": 648223624, "target": { "key": "a918a4a0a9882047261ff3aba6fa704d10590238685064c95888f0c1e4e03aeb" } } ], "extra": [ 1, 247, 45, 130, 135, 89, 232, 29, 148, 168, 138, 222, 242, 91, 55, 173, 73, 130, 212, 214, 56, 43, 110, 36, 237, 106, 129, 202, 101, 47, 67, 90, 138, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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